TB Angular upgrade 20#7141
Open
cdavalos7 wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation for features / changes
Part of a step-by-step Angular migration from v16 to v22. This PR upgrades the frontend from Angular 19 to Angular 20.
Technical description of changes
^20.0.0(resolved 20.3.25 in yarn.lock), @ngrx/* to ^20.0.0, and TypeScript to5.8.3@io_bazel_rules_webtestingfrom browsers-0.3.3 to browsers-0.3.4 to upgrade Chromium from Chrome 94 to Chrome 123tensorboard/tools/browserssince the default alias has restricted visibility and cannot be used from TensorBoard targetsspec_bundletarget to es2021 since Chrome 123 crashes on ES2022 class static blocks emitted by Angular npm packages.ng-reflect-*attributes removed inAngular 20, now reading from componentInstance or nativeElement instead.Detailed steps to verify changes work correctly (as executed by you)
Alternate designs / implementations considered (or N/A)